This bug is a regression since 0.511, right? Is it worth cherrypicking the fix into the 0.521 release?

This bug is a regression since 0.511, right?

I didn't do bisect, but I think this is very old, the code affected was last changed almost half year ago.

Actually it seems to be caused by 3589c08, Add support for NamedTuple methods (#3081) by @JelleZijlstra.

So actually few days after 0.511. Then formally speaking this is a regression.

So how confident are you? Anyway I'm testing this against the Dropbox codebase.

I think this should be quite safe (at least for sure not less safe than it was). There are only three possibilities: Instance, TupleType, and None. None can't happen, since this function is only called from within a class.

Merged, as it did not introduce new errors in our codebase. I will also cp.

Thanks for fixing the crash Ivan!

Arguably we should give an error for this case, since it breaks LSP. (If you take a tuple as an argument and use .count() on it, it will break if your tuple is actually a NamedTuple with a count attribute.) But that's less urgent.

But that's less urgent.

The error is shown (see test). I just re-use the fallback Instance to resolve the attribute type.